Data privacy
Live Hub provides data privacy and security controls that help organizations meet regulatory requirements and protect sensitive information throughout the data lifecycle. Its architecture, operational practices, and feature set follow industry standards and privacy regulations.
Privacy and compliance highlights
The certifications, controls and practices below govern how Live Hub handles your data.
Certified security and compliance
AudioCodes is certified for ISO 27001:2022, ISO 27032:2023 and SOC 2 Type 2. Live Hub is kept current with global privacy laws, including GDPR.
Data residency and encryption
Your data remains in the Microsoft Azure region you choose: Germany West Central, West Europe, East US, or Southeast Asia. AES 256-bit encryption is applied at rest and in transit. See Global region support for the Live Hub region each of these corresponds to.
Data minimization and retention
Live Hub collects and keeps only the personal data needed to run the service. Recordings and transcripts are deleted automatically on a schedule you set. See Recording and transcripts.
Role-based access control (RBAC)
Access to sensitive data, such as call recordings, transcripts, and configuration, is governed by granular RBAC, so that a user can reach only what their role requires. Microsoft Entra ID integration adds single sign-on (SSO) and multi-factor authentication (MFA).
Secure media and API handling
Media streams are encrypted with Secure Real-time Transport Protocol (SRTP). All external API communication, whether speech-to-text, translation, or AI services, uses HTTPS with TLS 1.2 or 1.3.
No customer data used for AI training
AudioCodes does not retain or use customer data to train AI models.
Where Live Hub calls a third-party provider, such as Azure OpenAI, Amazon Bedrock, Deepgram, or ElevenLabs, your data is sent only as far as that service needs it, and the provider's own privacy policy governs what happens next. Configuring the privacy options those vendors offer is your responsibility, not Live Hub's.
Features that support data privacy
Every feature that captures personal data is off until you enable it.
Call history privacy controls
You choose whether PII call metadata is stored for reporting and analytics. See Hide personal data.
Recording management
Recording is off by default. Enable it per bot connection or per routing rule, and set how long recordings are kept. See Call recording and Configure recording retention.
Transcription control
Transcription is off by default. Enable it per bot connection, and decide whether to share transcripts with AudioCodes support. See Call transcript.
Data residency selection
You select the Azure region in which your data is stored, so that it satisfies your compliance requirements. See Global region support.
Role-based access and SSO/MFA
You enforce least-privilege access and connect Live Hub to your enterprise identity provider. See Users and access and Policies and roles.